home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Giga Pack
/
Giga Pack CD1.iso
/
strategy
/
grid100
/
install.boi
< prev
next >
Wrap
Text File
|
1993-06-26
|
23KB
|
609 lines
This document is effective 6/27/93
INSTALL - BOI 2.05
BBS Onliner Interface
Copyright (C) 1990,1993 Andrew J. Mead
All Rights Reserved.
Introduction
This document is a basic installation guide to doors written with
the BBS Onliner Interface. A basic synopsis of the command line
arguments is given (please see COMMANDS.BOI), and examples (if
available) of installations under various BBS software are also
given. You should also read any door specific documentation as
well since this only covers the options of the BOI.
Sections
Command Line Directives
Again Play /A
Player Name /N
Quiet Local Console /Q
Limit Hall Of Fame /X
Redirect Hall Of Fame /Y
Maximum Time Limit /Z
Communications Directives
Locked Com Port /B
Specific BBS Installation Examples and Notes
Generic Installation
Batch File Example
Generic Installation
Command Line Example
2 A.M.
Auntie
DoorWay to Unlimited Doors
EIS-PC
Force
FoReM
Forum
GAP
Genesis
GT Power
Maximus (batch /R)
ModuleX
OLEcom
Opus 1.13
Opus 1.14
PCBoard 12.x
PCBoard 14.x
Phoenix
ProBoard
QuickBBS
RBBS (batch /R)
Remote Access (batch /R)
Renegade (batch /R)
RyBBS
Sapphire
Searchlight
Command Line Example (/9)
Simplex (batch /R)
Spitfire
TAG
Telegard
TPBoard
Virtual (batch /4, /S, or /Rn)
WildCat!
WWIV (batch /4)
Other Notes
DESQview
Windows
OS/2 and other multitaskers
File Sharing/Locking
What Went Wrong??? (or "Jane, how do I turn this thing off?")
Error messages
BBS Onliner Interface - Command Line Directives
Be sure to check out the door specific documentation about any
other command line directives that may be available.
Again Play (/A:x)
This option will allow players to play multiple games at one
sitting as long as they have as muchtime. If they have more
"x" minutes left (/a:x). This option carries no recommendation.
Player Name (/N:User_Name)
This switch is usually only necessary if the user information
is passed via command line instead of through a drop file (ie:
Searchlight BBS). It can also be used for at home play with a
batch file to make things simple.
Quiet Local Console (/Q)
This will keep the bell from beeping on the host computer. This
lets the SysOp to spleep at night, and it is highly recommended.
Limit Hall Of Fame (/X:n)
This options the player to a maximum of "n" appearences in the
Hall of Fame. I recommend /x:2 as this keeps one or two rabid
players from monopolizing the Hall of Fame.
Redirect Hall Of Fame (/Y:<path/filespec>
I heartily recommend using the text Hall of Fames as online
bulletins. The BBSs around here that use the bulletins tend
to have 5 to 10 times the play as the BBSs that don't. This
option is fully explained in COMMANDS.BOI.
Maximum Time Limit (/Z:x)
The BOI normally limits users to the amount of time specified
in the drop file. This option allows SysOps to set a maximum
upper limit. The game will execute an inactivity time-out at
approximately two minutes. It will beep at the halfway point
and then again when it returns control to the BBS.
Communications Directives (/C /I /K /L F)
Communications directives are beyond the scope of this
document. They are fully explained in COMMANDS.BOI.
Locked Com Ports (/B)
The BOI (when not using FOSSIL), uses RTS (UART Ready To
Send) handshaking. When you lock the DTE-DTC rate (your
computer to your modem) higher than the possible connect
rate between your modem and the remote (DTC-DTC rate), RTS
handshaking is insufficient, and may result in modem buffer
overruns and loss of data. Adding this switch implements
RTS/CTS (Modem Clear To Send) handshaking.
This switch is strongly RECOMMENDED if you do not use F+.
BBS Onliner Interface - Specific BBS Installation Examples and Notes
This is where you can help. I need samples. Please send me your
setup.
Generic Installation
Batch File Example
Until more examples arrive please check WWIV example.
Command Line Example
Until more examples arrive please check Searchlight example.
2 A.M. BBS
The /2 option reads JUMPER.DAT. Installation example not
available.
Auntie BBS
The /7 option reads a file called AUNTIE.SYS. My information
on Auntie BBS is extremely limited, and you will also need to
supply the door with the communications information (/C or /I).
Installation example not available.
DoorWay to Unlimited Doors
The /S options reads the "short" DOOR.SYS file. Installation
example is not available.
EIS-PC
The /Rx option reads DORINFOx.DAT. Installation example is not
available.
Force
The /S options reads the "long" DOOR.SYS file. This is a
proposed standard format for drop files. Installation example
is not available.
FoReM
The /Rx option reads DORINFOx.DAT. Installation example is not
available.
Forum
The /F option reads USERINFO.TXT. Installation example not
available.
GAP
The /S options reads the "long" DOOR.SYS file. This is a
proposed standard format for drop files. Installation example
is not available.
Genesis
The support for Genesis' CALLINFO.BBS is untested. If you try
this /G option, please let me know whether or not it works.
GT Power
The /0 option reads GT Power's GTUSER.BBS file. There is one
crucial piece of information missing from the file, however.
GTUSER.BBS does not tell what commport the BBS is using. If you
are running the BBS on COM1, you need not worry about anything,
but if you are not, you will need to use either the /C:x or the
/I:i:nnnn command. I would like to thank Steven Wright for his
help in getting this option working.
Maximus
The BOI is able to read many of the various drop files that
Maximus can create.
This example is courtesy of Robert McClure:
<<Maximus Menus.CTl file in Game Menu section add two lines>>
Display_File C:\Max\Misc\Dorinfo Disgrace "1 Door Game"
NoDsp Xtern_Dos C:\Max\Doorgame.Bat Disgrace "1"
<<In C:\Max create a batch File:>>
cd c:\Doors\Gamedoor (Directory were GameDoor resides)
GameDoor /R1:C:\Max\ /q /a
cd\max
Not sure if its required but also have the following mecca token
on the Welcome.mec: [link]c:\max\misc\Dorinfo
These examples are courtesy of Peter Hebert:
METHOD 1
--------
This goes in GAMEDOOR.MEC:
[yellow]Loading GameDoor...[
][link]misc\dorinfo [
][xtern_dos]c:\gamedoor\gamedoor /r1:c:\max\ /b /x:2 /q /a:15
And this goes in MENUS.CTL:
Display_File Misc\GameDoor Disgrace "B) GameDoor"
Of course you have to compile the MEC file with MECCA and reSILT
your menus after you do this.
METHOD 2
--------
Both lines go in MENUS.CTL:
Display_File Misc\Dorinfo Disgrace "B) GameDoor"
Xtern_Dos c:\gamedoor\gamedoor_/r1:c:\max\_/b_/x:2_/q_/a:15
Disgrace "B"
(that second line is all one line, in case your editor / my editor
chops it).
I prefer the former method because it allows me to put in the
little message ("Loading GameDoor...") for each door, but it's one
less text file cluttering your MISC\ directory if you do it the
second way. Multinode systems may have to make changes to the
paths or the node number depending on where/what name they give the
drop file.
ModuleX
The /M option reads NUMBER.TXT. Installation example not
available.
OLEcom
The /Rx option reads DORINFOx.DAT. Installation example is not
available.
Opus-CBCS 1.13
My documentation on Opus 1.13's drop file(s) is incomplete. I'd
appreciate any help.
Opus-CBCS 1.14
The /Oxx option reads LASTUSxx.DAT (where xx is the Opus task
number in hexadecimal, if xx is not present the door looks for
a file called LASTUSER.DAT.). Example:
doorgame /o0e:c:\opus\
the c:\opus\ tells it to look for LASTUS0E.DAT in the C:\OPUS\
directory. Complete installation example is not available.
PCBoard 12.x
The /1 option reads PCBOARD.SYS. My documentation on this file
is incomplete, and I'd appreciate any additional information.
Installation example not available.
PCBoard 14.x
The /P option reads PCBOARD.SYS. As per PCBoard specifications
the BOI will blank out most of this file if the user drops
carrier while in the door. Installation example not available.
Phoenix
The /H option reads INFO.BBS. Installation example not
available.
ProBoard
I would really appreciate any information about dropfiles that
ProBoard creates. Installation examples would also be nice.
QuickBBS
The /Rx option reads DORINFOx.DAT. Installation example is not
available.
RBBS
The /Rx option reads DORINFOx.DAT. The follow installation
example is courtesy of Arnold Robinson.
RBBS directory -> C:\RBBS
batch file directory -> C:\RBBS
batch file -> DOORGAME.BAT
doorgame directory -> C:\RBBS\DOOR
(DOORGAME.EXE, DOORGAME.INS, DOORGAME.LNG, DOORGAME.KEY)
bulletins directory -> C:\RBBS\BULLETIN
RBBS config parm 109 -> DOORS.DEF
Put this line in C:\RBBS\DOORS.DEF
"DOORGAME",10,,D,"DOORGAME.BAT",N,,30
what the values mean (most are optional), the values ar not
necessarily recommendation, merely what Arnold uses.
"DOORGAME" - name of door
10 - securitly level
(blank) - questionaire to execute
D - "D"rop or "S"hell to door
"DOORGAME.BAT" - batch file to run
N - ask for password on return (Y/N)
(blank) - file to display on return
30 - max time allowed in door
C:\RBBS\DOORGAME.BAT listing
@echo off
cd c:\rbbs\door
doorgame /r1c:\rbbs\ /yc:\rbbs\bulletin\ /q /x:2 /a /b
cd c:\rbbs
Remote Access
Remote Access can run doors in several different ways (Type 7,
Type 15, command line). The BOI should be able to handle all
of those using either DORINFOx.DAT or DOOR.SYS. The /Rx option
reads DORINFOx.DAT. The following example is courtesy of Jan
Rundquist. I believe he uses a Type 7 exit.
RA directory -> C:\RA
batch file directory -> C:\RA
batch file -> DOORGAME.BAT
doorgame directory -> C:\RA\DOORS\DOORGAME
(DOORGAME.EXE, DOORGAME.INS, DOORGAME.LNG, DOORGAME.KEY)
bulletins directory -> C:\RA\TXTFILES
"DOORGAME" - name of door
"DOORGAME.BAT" - batch file to run
SINGLE NODE setup
-----------------
The following should be entered in optional data field in
your RA menu.
*C /c C:\RA\DOORGAME.BAT
C:\RA\DOORGAME.BAT for single node
@echo off
cd c:\ra\doors\doorgame
doorgame /R1:c:\ra\ /A:5 /Q /X:2 F+ -T /Y:c:\ra\txtfiles\
exit
MULTI NODE setup
----------------
The following should be entered in optional data field in
your RA menu.
*C /c C:\RA\DOORGAME.BAT *N
*N gets the current node
C:\RA\DOORGAME.BAT for multi node
@echo off
cd c:\ra\doors\doorgame
doorgame /R1:c:\ra\line%1 /A:5 /Q /X:2 F+ -T /Y:c:\ra\txtfiles\
exit
%1 is replaced with the value of *N
Renegade
Renegade supports many door file formats, given as an example is
DORINFOx.DEF, however. The /Rx option reads in DORINFOx.DEF,
where x is the node number. This example was supplied by Dennis
Alexander.
Go to the menu edit command ("#" at the SysOp menu) and
"M"odify your online games menu.
1. Long Descript : <description of door here>
2. Short Descript: <description of door here, short>
3. Menu Keys : <command, example- "D" for "Door">
4. ACS Required : <access level, example "VV" (validated users)>
5. CmdKeys : DD <use DORINFOx.DEF, others: DC,DG,DS,DW,D->
6. Options : DOOR.BAT %N <name of batch file to run, make
this different for each seperate door you use>
An example DOOR.BAT listing
@echo off
cd c:\bbs\doors
doorgame /r%1:c:\bbs /q /a
cd c:\bbs
exit
RyBBS
The /5 option reads CURRUSER.BBS. Installation example not
available.
Sapphire
My documentation on Sapphire's SAPPHIRE.DAT is incomplete. I
would appreciate any further information on what dropfiles that
Sapphire creates.
Searchlight
I do not have any information regarding any drop files that
Searchlight creates.
Command Line Example
The BOI allows BBSes to pass information to it via command
line. This bypasses the need for batch files. By using the
/9 switch, the BOI knows to get the information it needs
from the command line. The /9 tells the BOI where to find
the door and its associated files. For example
c:\slbbs\games\doorgame /9
This command tells the BOI that all extra files (data files,
hall of fames, etc...) should be kept in c:\slbbs\games\.
You will also need to tell the BOI the user's name, the
amount of time the user has left, and the commport. You
might try the following:
c:\slbbs\games\doorgame /9 /n%U /z%M /c:%P (...)
The %U passes the door the users name (Andrew_Mead), the
%M passes the time remaining in minutes, and the %P tells
the door what commport is in use. The elipses (...) just
represents the other switches you might choose to use.
Simplex
The /Rx option reads DORINFOx.DAT. The follow installation
example is courtesy of Al Polenz.
Simplex directory -> C:\SIMPLEX
batch file directory -> C:\SIMPLEX
batch file -> DOORGAME.BAT
doorgame directory -> C:\SIMPLEX\DOOR
(DOORGAME.EXE, DOORGAME.INS, DOORGAME.LNG, DOORGAME.KEY)
bulletins directory -> C:\SIMPLEX\SCREENS
C:\SIMPLEX\DOORGAME.BAT listing
@echo off
cd c:\simplex\door
doorgame /r1c:\simplex\ /yc:\simplex\screens\game.scr /q /x:2 /a
cd c:\simplex
exit
Spitfire
The /6 option reads SFDOORS.DAT. Installation example is not
available.
TAG
The /Rx option reads DORINFOx.DAT. Installation example is not
available.
Telegard
I believe that Telegard creates CHAIN.TXT, and installation is
probably similiar to that of WWIV.
TPBoard
The /Rx option reads DORINFOx.DAT. Installation example is not
available.
Virtual
Virtual BBS can create several different drop files.
Here is an example (courtesy Patrick Murray). I recommend using
the /4 (CHAIN.TXT) command, as it shows both user name and
handle. You can also use /Rn (DORINFOn.DEF) and /S (long
DOOR.SYS).
CHAIN.TXT directory -> C:\VBBS
batch file directory -> C:\VBBS\GAMES
batch file -> DOOR.BAT
doorgame directory -> C:\VBBS\GAMES\DOOR
(DOORGAME.EXE, DOORGAME.INS, DOORGAME.LNG, DOORGAME.KEY)
bulletins directory -> C:\VBBS\GAMES\HOF
VConfig / Doors settings
1. Program Name: DoorGame (ANSI)
2. Command Line: C:\VBBS\GAMES\DOOR.BAT
C:\VBBS\GAMES\DOOR.BAT listing
@echo off
cd c:\vbbs\games\door
doorgame /4c:\vbbs\ /yc:\vbbs\games\hof\ /q /x:2 /a /b
cd c:\vbbs
WildCat!
The /W option reads CALLINFO.BBS of WildCat! 2.x and the /S
option reads the DOOR.SYS of WildCat! 3.x. Installation
examples are not available.
WWIV
The /4 option reads CHAIN.TXT. This is the setting that I use
on my BBS (The Infinite Improbability BBS, @9952 WWIVnet). The
sample is for DOORGAME.EXE
CHAIN.TXT directory -> C:\WWIV
batch file directory -> C:\WWIV\GAMES
batch file -> door.bat
doorgame directory -> C:\WWIV\GAMES\DOOR
(DOORGAME.EXE, DOORGAME.INS, DOORGAME.LNG, DOORGAME.KEY)
bulletins directory -> C:\WWIV\GFILES\HOFSDIR
//CHAINEDIT settings
A. Description : DoorGame (ANSI)
B. Filename : C:\WWIV\GAMES\DOOR.BAT
E. ANSI : Required <--- Optional
F. DOS Interrupt: NOT Used <--- You need this
G. 300 Baud : NOT Allowed <--- Recommended
H. Shrink : No <--- loads faster
C:\WWIV\GAMES\DOOR.BAT listing
@echo off
cd c:\wwiv\games\door
doorgame /4c:\wwiv\ /yc:\wwiv\gfiles\hofsdir\ /q /x:2 /a /b
cd c:\wwiv
BBS Onliner Interface - Other Notes
DESQview
The BBS Onliner Interface is DESQview aware. It will give up
time to other applications while waiting for input. If the
internal async routines are active, it will also alert DESQview
when it is in a critical state.
Some notes are filtering in about QEMM complaining about the
command line. One user stated he got the door working by
removing the extraneous colons from the command line.
/sc:\bbs\ instead of /s:c:\bbs\
I do not understand any of this, but it might help you out. If
anyone can document any problems with QEMM or DESQview please
contact me.
Windows, OS/2 and other DOS multitaskers
The BBS Onliner Interface will give up time slices to all DOS
based multitaskers that play by DOSes rules. I have verified
reports that since this capability was added, Windows sessions
in other windows are now much, much faster.
File Sharing/Locking
The BBS Onliner Interface now supports rudimentary file sharing
and locking. If the author of the door has used the built in
file handling routines, then the door should run well in multi-
node environments.
What Went Wrong??? (or "Jane, how do I turn this thing off?")
Program Crashes at end of game.
You probably have a corrupted Hall of Fame data file.
Check the door specific documentation as to what files
might be involved.
Error messages
Currently defined error messages that you will find in
BOI.LOG, their causes, and possible solutions.
error explained
2 Unkown or incorrect argument on command line.
3 Unsupported file format. Please send me any and all
information you might have on your BBS software's
drop file, and I'll add support for it.
4 Unable to find file.
5 Error in file. This means that file does not match
the structure that I have for it. If you are using
a DOOR.SYS drop file, try using the other one (/S /D)
6 /Z:nn out of range or non-numeric
7 Duplicate directives.
8 Path/Filename for Hall of Fame is not valid. You
have given the /Y switch an invalid path/filespec.
9 Path not valid.
11 Invalid or missing number in /X:nn switch.
12 /X:nn value out of range. This must be between 1-19.
13 Invalid or missing value in /C:n. "n" must be a
valid port number. 1 to 4 if you are not using a
FOSSIL driver, and 1 to 8 if you are.
16 /L can not be used with either /C or /I.
17 Invald format in /I:i:nnnn. The nnnn must use all
four spaces.
18 Invald hexadecimal in /I:i:nnnn.
19 Invalid numeric in /A:x.
20 /A:x time value must be at least 5 minutes.
31 Unable to find/initialize FOSSIL driver. Please
notify me, and check your setup. This switch should
only occur if you use the F+ switch.
BBS Onliner Interface
Copyright (C) 1990, 1993 Andrew J. Mead
All Rights Reserved.
Contact:
Andrew J. Mead
PO BOX 1155
Chapel Hill, NC 27514-1155
USA
1@9952 WWIVnet
1@9395 VirtualNet
1:3641/417 FidoNet
75:7919/417 DoorNet
+919 489 9446 - PCP:NCRTP - V32BIS - 24HRS
END INSTALL.BOI